System and method for transmitting orthopaedic implant data

ABSTRACT

A system and method for transmitting implant data includes an orthopaedic implant, a wireless receiver, and a processing circuit electrically coupled to the wireless receiver. The orthopaedic implant is configured to transmit implant identification data and implant sensor data to the wireless receiver in response to a power signal. The orthopedic implant may transfer the data over, for example, a wireless network. The processing circuit receives the implant identification data and the implant sensor data from the wireless receiver and is configured to retrieve patient-related data from a database based on the implant identification data. The processing circuit may also be configured to update a patient queue, assign a patient room to a patient, and/or transmit the patient-related data and the implant sensor data to a client machine located in the patient room.

CROSS-REFERENCE TO RELATED U.S. PATENT APPLICATION

Cross-reference is made to U.S. Utility patent application Ser. No.______ entitled “System and Method for Managing Patient-Related Data,”which was filed Apr. 7, 2006 by Mark R. DiSilvestro et al., the entiretyof which is expressly incorporated herein by reference.

TECHNICAL FIELD

The present disclosure relates generally to systems and methods formanaging patient-related data.

BACKGROUND

Prior to a medical examination, surgical, or other medical appointment,a patient must typically register with a receptionist or other personnelof the doctor's office or hospital wherein the examination or surgicalprocedure will be performed. During the registration process, thepatient may be required to supply or verify information related to hisor her identify and/or medical history. The receptionist uses theinformation supplied by the patient to manually retrieve medical recordsphysically stored at the doctor's office or hospital and/or stored onthe doctor's office or hospital's network. The patient is typicallyrequired to provide any additional information required for the medicalexamination or surgical procedure.

The patient is also typically required to “sign-in” on a patient list,which is manually updated by the receptionist as patient examinations orsurgical procedures are completed and patient rooms become available.Once a patient room is available for the new patient, the receptionistor other caregiver notifies the patient and manually transfers theretrieved medical records to the assigned patient room for the doctor'sreview.

SUMMARY

According to one aspect, an orthopaedic implant includes a housinghaving an aperture defined therein and a secondary coil positioned inthe aperture. The secondary coil may include a number of turnspositioned so as to define a reference plane. The reference plane may besubstantially parallel to a sagittal plane of a body of a patient withthe orthopaedic implant is implanted in the patient. The orthopedicimplant may be, for example, a tibial tray. The orthopaedic implant mayalso include a processing circuit electrically coupled to the secondarycoil. The processing circuit may be configured to receive a power signalfrom the secondary coil when the secondary coil is inductively coupledwith a primary coil. The orthopaedic implant may also include a wirelesstransmitter coupled to the processing circuit and an antenna coilelectrically coupled to the wireless transmitter. The processing circuitmay be configured to control the wireless transmitter to transmitimplant identification data in response to the power signal using theantenna coil. The orthopaedic implant may also include one or moresensors such as, for example, a pressure sensor, a load sensor, atemperature sensor, and/or a hall-effect sensor. The processing circuitmay be configured to receive an output signal from the sensor(s) andcontrol the wireless transmitter to transmit the output signal inresponse to the power signal using the antenna coil. The transmitter maybe configured to transmit the implant identification data and/or theoutput data using a wireless local area network frequency. For example,the transmitter may transmit the implant identification data and/or theoutput data at a frequency of about 2.4 gigahertz. Additionally oralternatively, the transmitter may transmit such data using a Bluetoothtransmission protocol.

According to another aspect, a method for transmitting data from anorthopaedic implant includes receiving a power signal generated by aprimary coil with a secondary coil of the orthopaedic implant. Forexample, the secondary coil may receive the power signal bytranscutaneously receiving an amount of energy from the primary coil.The power signal may, for example, power a processing circuit and/ortransmitter of the orthopaedic implant. The method may also includereceiving an output signal from a sensor of the orthopaedic implant inresponse to the power signal. The sensor may be, for example, a pressuresensor, a load sensor, a temperature sensor, and a hall-effect sensor.The method may further include wirelessly transmitting implantidentification data and the output signal in response to the powersignal. The implant identification data and the output signal may betransmitted using a wireless local area network frequency such as, forexample, a frequency of about 2.4 gigahertz. Additionally oralternatively, the implant identification data and the output signal maybe transmitted using a Bluetooth transmission protocol. The implantidentification data and the output signal may be transmitted to awireless router.

According to a further aspect, a system for managing patient-relateddata may include an orthopaedic implant having a secondary coil, aprimary coil, and a wireless receiver. The orthopaedic implant may beconfigured to transmit implant identification data and implant sensordata in response to a power signal. For example, the orthopaedic implantmay be configured to transmit the implant identification data and theimplant sensor data using a wireless local area network frequency suchas, for example, a frequency of about 2.4 gigahertz. Additionally oralternatively, the orthopaedic implant maybe configured to transmit theimplant identification data and the implant sensor data using aBluetooth transmission protocol. The primary coil may be configured toinductively couple with a secondary coil of the orthopaedic implant toprovide the power signal to the orthopaedic implant. The primary coilmay be coupled, for example, coupled to a gate configured to allowpatients to travel therethrough. The wireless receiver configured toreceive the implant identification data and the implant sensor datatransmitted by the orthopaedic implant. The wireless receiver may be,for example, a wireless router.

The system may also include a processor coupled to the wireless receiverand a memory device electrically coupled to the processor. The memorydevice may have stored therein a plurality of instructions, which whenexecuted by the processor, cause the processor to receive the implantidentification data and the implant sensor data from the wirelessreceiver and retrieve patient-related data from a database based on theimplant identification data. For example, the processor may retrieve thepatient-related data from a database of a hospital network. Theplurality of instructions may further cause the processor to update anelectronically-stored patient queue based on the retrieving step.Additionally, the plurality of instructions may further cause theprocessor to assign a patient room to a patient identified by thepatient-related data based on the electronically-stored patient queue.The plurality of instructions may also cause the processor to transmitthe patient-related data and the output sensor data to a client machinelocated in the patient room. The plurality of instructions may yetfurther cause the processor to determine the availability of the patientroom based on the electronically-stored patient queue and provide anelectronic notification if the patient room is available. For example,the processor may activate a public address system or display a name ofa patient identified by the patient-related data on a display screen.The plurality of instructions may also cause the processor to transmitthe patient-related data and the implant sensor data to a client machineand/or a portable media device over a wireless network.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description particularly refers to the following figures,in which:

FIG. 1 is a simplified block diagram of a system for managingpatient-related data;

FIG. 2 is a perspective view of an implant identification reader of thesystem of FIG. 1;

FIG. 3 is a elevated from view of the implant identification reader ofFIG. 2;

FIG. 4 is a perspective view of an orthopaedic implant usable with thesystem of FIG. 1;

FIG. 5 a is a cross-sectional, lateral-to-medial view of one embodimentof a secondary coil assembly of the orthopaedic implant of FIG. 4;

FIG. 5 b is a cross-sectional, anterior-to-posterior view of thesecondary coil assembly of FIG. 5 a;

FIG. 5 c is a cross-sectional, lateral-to-medial view of anotherembodiment of a secondary coil assembly of the orthopaedic implant ofFIG. 4;

FIG. 5 d is a cross-sectional, lateral-to-medial view of anotherembodiment of a secondary coil assembly of the orthopaedic implant ofFIG. 4;

FIG. 6 is a simplified block diagram of an electrical circuit of theorthopaedic implant of FIGS. 4 and 5 a-5 d;

FIG. 7 is a simplified block diagram of another embodiment of theelectrical circuit of FIG. 6;

FIG. 8 is a simplified block diagram of another embodiment of the systemof FIG. 1;

FIG. 9 is a simplified flowchart of an algorithm for transmittingimplant data that is executed by the electrical circuits of FIGS. 6and/or 7; and

FIG. 10 is a simplified flowchart of an algorithm for managingpatient-related data that is executed by the systems of FIGS. 1 and/or8.

DETAILED DESCRIPTION OF THE DRAWINGS

While the concepts of the present disclosure are susceptible to variousmodifications and alternative forms, specific exemplary embodimentsthereof have been shown by way of example in the drawings and willherein be described in detail. It should be understood, however, thatthere is no intent to limit the concepts of the present disclosure tothe particular forms disclosed, but on the contrary, the intention is tocover all modifications, equivalents, and alternatives falling withinthe spirit and scope of the invention as defined by the appended claims.

Referring to FIG. 1, a system 10 for managing patient-related dataincludes a controller 12 communicatively coupled to an implantidentification reader 14 via a communication link 16. The controller 12illustratively includes a processor 18 and a memory device 20. Theprocessor 18 may be embodied as any type of processor including, forexample, discrete processing circuitry (e.g., a collection of logicdevices), general purpose integrated circuit(s), and/or applicationspecific integrated circuit(s) (i.e., ASICs). The memory device 20 maybe embodied as any type of memory device and may include one or morememory types, such as, random access memory (i.e., RAM) and/or read-onlymemory (i.e., ROM). In addition, the controller 12 may include otherdevices and circuitry typically found in a computer for performing thefunctions described herein such as, for example, a hard drive,input/output circuitry, and the like.

The controller 12 is communicatively coupled to a number of clientmachines 22, 24 via a network 34. The client machines 22, 24 may beembodied as any type of computer or computing device capable ofdisplaying data to a user and receiving input from the user. Forexample, the client machines 22, 24 may be embodied as “dumb terminals”and include a display device, an input device such as a keyboard, andminimal peripherals. Alternatively, one or more of the client machines22, 24 may be embodied as a typical desktop or laptop computer equippedwith a display screen, keyboard, and other devices and circuitrytypically found in a desktop and/or laptop computer. Illustratively, thesystem 10 includes one or more receptionists client machines 22 and oneor more remote client machines 24. The receptionist's client machines 22are located in the reception area of the doctor's office or hospitalwherein the system 10 is incorporated and usable by a receptionist ornurse to monitor a patient queue, patient room availability, and thelike.

Each of the remote client machines 24 may be located in a patient roomsuch as a patient examination room or operating room of the doctor'soffice or hospital wherein the system 10 is incorporated. Additionallyor alternatively, a remote client machine 24 may be located outside eachpatient room, in the doctor's or other caregiver's office, or in anyother location of the doctor's office or hospital. The remote clientmachines 24 may be used by the doctors, nurses, or other caregivers toreview and update patient-related data prior to, during, or subsequentto the examination, surgery, or other medical procedure. As used herein,the term patient-related data refers to any data related to a particularpatient and may include, but is not limited to, patient medical records,X-rays, patient identification data, or the like.

The controller 12 is also coupled to one or more portable media devices26 via the network 34. The portable media devices 26 may be embodied asany device capable of receiving data from the controller 12 anddisplaying such data to a user of the device 26. For example, theportable media device may be embodied as a personal digital assistant(PDA), portable laptop computer, or the like. The portable media device26 may also be configured to receive input data from the user andtransfer such data to the controller 12. As such, the portable mediadevices 26 may be used by the doctors, nurses, and/or other caregiversof the doctor's office or hospital wherein the system 10 is incorporatedto remotely receive and/or transmit data to the controller 12.

The controller 12 is additionally coupled to one or more printers 28, apublic address system 30, and a patient database 32 via the network 34.The printer(s) 28 may be any type of printer controllable by thecontroller 12. For example, the printer may be embodied as a dot-matrixprinter, a ink jet printer, a laser printer, or the like. The printer(s)28 may be located in the reception area of the doctor's office orhospital such that the printer 28 is accessible by the receptionist.Additionally or alternatively, one or more of the printers 28 may belocated in a doctor's office or any other location wherein a printedcopy of data may be required.

The public address system 30 may be embodied as any type of systemcapable of providing information to the patients of the doctor's officeor hospital wherein the system 10 is incorporated. The public addresssystem 30 may be embodied as a visual public address system, an audibleaddress system, or a combination thereof. For example, the publicaddress system 30 may be embodied as a loudspeaker located in a waitingarea of the doctor's office or hospital. Additionally or alternatively,the public address system 30 may be embodied as a large display screenlocated in or viewable from the waiting area.

The patient database 32 may be embodied as any type of database capableof storing patient-related data. Although illustrated in FIG. 1 as asingle database, it should be appreciated that the patient database 32may be embodied as any number of separate databases, file folders, flatfiles, or other storage locations. As discussed in more detail below inregard to FIG. 10, the patient-related data stored in the database 32 isstored in association with, indexed by, or otherwise retrievable basedon implant identification data. The patient database 32 may be locatedin the doctor's office or hospital wherein the system 10 is incorporatedor may be located remotely therefrom. In one particular embodiment, thepatient database 32 forms a portion of a hospital network that isaccessible by the controller 12 via the network 34.

The network 34 may be embodied as any type of network capable offacilitating communication between the controller 12 and the clientmachines 22, 24, the portable media devices 26, the printers 28, thepublic address system 30, and the patient database 32. For example, thenetwork 34 may be a local area network (LAN), a wide area network (WAN),or form a portion of a publicly-accessible, global network such as theInternet. In addition, the network 34 may be a wired network, a wirelessnetwork, or a combination thereof. The controller 12 is communicativelycoupled to the network 34 via a communication link 36. The clientmachines 22, 24 are coupled to the network 34 via communication links38, 40, respectively. The portable media devices 26 are communicativelycoupled to the network 24 via communication links 42. The printers 28and the public address system 30 are communicatively coupled to thenetwork 34 via communication links 44, 46, respectively. Additionally,the patient database 32 is communicatively coupled to the network 34 viacommunication links 48. The communication links 36, 38, 40, 42, 44, 46,and 48 may be any type of communication link capable of facilitatingcommunication between the controller 12 and the client machines 22, 24,the portable media devices 26, the printers 28, the public addresssystem 30, and the patient database 32. For example, the communicationlinks 36, 38, 40, 42, 44, 46, and 48 may be embodied as any number ofwires, cables such as fiber optic cables, or the like. Additionally, anyone or more of the communication links 36, 38, 40, 42, 44, 46, and 48may be embodied as wired or wireless communication links. In embodimentswherein the communication links 36, 38, 40, 42, 44, 46, and 48 arewireless communication links, the controller 12, the client machines 22,24, the portable media devices 26, the printers 28, the public addresssystem 30, and/or the patient database 32 may include a wirelesstransmitter and/or receiver to facilitate wireless communication withthe network 34.

The implant identification reader 14 includes a primary/receiver coil50. The primary/receiver coil 50 is configured to be inductively coupledto a secondary coil of an orthopaedic implant 52 located in a patient 54as discussed in more detail below in regard to FIGS. 2-5. Theprimary/receiver coil 50 may be any type of coil capable of generatingan electromagnetic field to transcutaneously transfer an amount ofenergy to the orthopaedic implant and receive data therefrom. Theimplant identification reader 14 may be located at an entrance of thedoctor's office or hospital wherein the system 10 is incorporated. Theprimary/receiver coil 50 is positioned in the implant identificationreader 14 such that the orthopaedic implant 52 is positioned within theelectromagnetic field generated by the primary receiver coil 50 when thepatient 54 walks by the implant identification reader 14.

In use, the controller 12 energizes the primary/receiver coil 50 bysupplying a power signal to the primary/receiver coil 50 via thecommunication link 16. The controller 12 may energize theprimary/receiver coil 50 continuously, periodically, or in response tothe presence of the patient 54. For example, a motion or load sensor maybe located near the implant identification reader 14 to sense thepresence of the patient 54. When the sensor detects that the patient 54is near the implant identification reader 14, the sensor may transmit aoutput signal to the controller 12. In response to the output signal,the controller 12 may be configured to transmit the power signal to theprimary/receiver coil 50 to cause the primary/receiver coil 50 togenerate the electromagnetic field and thereby inductively couple withthe secondary coil of the orthopaedic implant 52. In response to theelectromagnetic field, the orthopaedic implant 52 is configured totransmit implant identification data as discussed below in regard toFIG. 9. The implant identification data may be embodied as any type ofdata that uniquely identifies the orthopaedic implant 52. For example,the implant identification data may be embodied as a code or password.The implant identification data is received by the primary/receiver coil50 of the implant identification reader 14 and transmitted to thecontroller 12 via the communication link 16. In response to the implantidentification data, the controller 12 is configured to retrievepatient-related data. As discussed in more detail below in regard toFIG. 10 a-c, the controller 12 may also be configured to transmit thepatient-related data to the client machines 22, 24 and/or the portablemedia device 26, control the printer 28 to print a patient informationform to update the patient-related data, and/or control the publicaddress system 30 to notify the patient when a patient room isavailable.

Referring now to FIGS. 2 and 3, in one illustrative embodiment, theimplant identification reader 14 is embodied as a gate 70. The gate 70includes a base 72, a first side wall 74, and a second side wall 76. Thefirst and second side walls 74, 76 define a passageway 78 therebetween.The gate 70 is configured to be located near an entrance of the doctor'soffice or hospital wherein the system 10 is incorporated such that thepatient 54 is required to walk through the passageway 78 when thepatient 54 enters the office or hospital. In the illustrative gate 70, aprimary/receiver coil 50 is positioned in each of the side walls 74, 76.However, in other embodiments, only one of the side walls 74, 76 mayinclude a primary/receiver coil 50. The primary/receiver coils 50 areembodied as spiral coils such that the turns of the coils 50 are locatedin reference planes 82, 84. The primary/receiver coils 50 are positionedin the side walls 74, 76 such that the reference planes 82, 84 aresubstantially parallel with a sagittal plane 80 of the patient 54 whenthe patient 54 walks through the passageway 78.

Referring now to FIGS. 4 and 5 a-5 d, in one illustrative embodiment,the orthopaedic implant 52 may be embodied as a tibial tray 100. Thetibial tray 100 includes a platform 102 and a stem 104 configured to beimplanted in a tibia bone of the patient 54. The platform 102 includes atop surface 106 having an aperture 105 configured to receive a polymerbearing (not shown). A secondary coil housing 108 is coupled to a distalend of the stem 104. The housing 108 may be formed from any suitablematerial which does not interfere with the functioning of the circuitry(e.g., the secondary coil and other circuitry as described below)included therein such as a polymer material. The housing 108 may becoupled to the stem 104 using any suitable coupling mechanism. Forexample, the housing 108 may include a screw portion 112 (see FIGS. 5a-5 d) configured to be mated with a threaded aperture defined in thestem 104. Alternatively, the housing 108 may be coupled to stem 104 viaa twist-lock mechanism. Moreover, in some embodiments, the housing 108may be coupled to the stem 104 via any suitable type of adhesive or thelike.

The housing 108 includes an aperture 114 defined therein. A secondarycoil 116 is positioned in the aperture 114. In one embodiment, asillustrated in FIGS. 5 a and 5 b, the secondary coil 116 is secured to abobbin 118 which is position in the chamber 114 and secured to thehousing 108 in a fixed position. The bobbin 118 may be secured to thehousing 108 in the chamber 114 using any suitable securing means suchas, for example, press-fitting, an adhesive, securing devices such asscrews or bolts, or the like.

The secondary coil 116 is formed from a number of coil turns defined ona coil receiving portion 119 of the bobbin 118. The illustrative bobbin118 has a substantial “I” shape and includes a number apertures 122through which the coil turns of the secondary coil 116 pass such thatthe secondary coil 116 may be formed from any number of coil turns. Thecoil turns of the secondary coil 116 are formed on the bobbin 118 suchthat the coil turns are located in a reference plane 120. The secondarycoil 116 also includes coil terminal ends 124 that extend from thehousing 108 via a passageway (not shown) defined in the screw portion112. The secondary coil 116 is electrically coupled to electroniccircuitry via the coil terminal ends 124 as discussed below in regard toFIGS. 6 and 7. Alternatively, the secondary coil 116 may be electricallycoupled to electronic circuitry via two or more contacts (not shown)established on a top surface 126 of the screw portion 112. The contactsmay be configured to mate with similar contacts established on the stem104 when the housing 108 is coupled thereto. The electronic circuitrymay be coupled to the contacts of the stem 104 such that the electroniccircuitry is electrically coupled to the secondary coil 116 via themated contacts when the housing is coupled to the stem 104. Suchelectronic circuitry may be positioned in a suitable aperture of thestem 104 and/or the platform 102. Additionally or alternatively, aportion of the electronic circuitry may be positioned in the housing 108with the secondary coil 116.

In the embodiment illustrated in FIGS. 5 a and 5 b, the bobbin 118 ispositioned and secured in the stem 104 of the tibial tray 100 such thatthe reference plane 120 formed from the coil turns of the secondary coil116 are substantially parallel with the sagittal plane 80 of the patient54 when the tibial tray 100 is properly implanted in the patient 54. Insuch a configuration, as illustrated in FIG. 3, when the patient 54passes through the passageway 78 of the gate 70, the reference plane 120defined by the coil turns of the secondary coil 116 of the orthopaedicimplant 52 (e.g., the tibial tray 100) is substantially parallel withthe reference planes 82, 84 defined by the coil turns of theprimary/receiver coils 50. As such, because the secondary coil 116 andthe primary/reference coil 50 are substantially parallel, the inductivecoupling of the coils 50, 116 may be improved.

Alternatively, as illustrated in FIG. 5 c, the secondary coil 116 issecured to a bobbin 130 that is positioned in the chamber 114. Similarto bobbin 118, the bobbin 130 may positioned in the chamber 114 andsecured to the housing 108 using any suitable securing means such as,for example, press-fitting, an adhesive, securing devices such as screwsor bolts, or the like. The bobbin 130 has a substantial circularcross-section and includes a round coil receiving portion 132 definedbetween a first and second end plate 134, 136. The coil turns of thesecondary coil 116 are formed on the coil receiving portion 132 suchthat the coil turns are located in the reference plane 120. Similar tothe bobbin 118 described above in regard to FIGS. 5 a and 5 b, thebobbin 130 is positioned and secured in the chamber 114 of the housing108 such that the reference plane 120 formed from the coil turns of thesecondary coil 116 are substantially parallel with the sagittal plane 80of the patient 54 when the tibial tray 100 is properly implanted in thepatient 54. Although the illustrative coil receiving portion 132 has asubstantial round shape, it should be appreciated that in otherembodiments, bobbins having any coil receiving portions of any shape maybe used. For example, bobbins having oval, square, and/or rectangularcoil receiving portions may be used.

In another embodiment, as illustrated in FIG. 5 d, the secondary coil116 is secured to a bobbin 140 that is positioned in the chamber 114.The bobbin 140 includes a coil receiving portion 142 similar to the coilreceiving portion 119 of the bobbin 118. The bobbin 140 also includesfirst and second end plates 142, 144 having a length 147 substantiallyequal to an inner diameter of the chamber 114 such that the bobbin 140may be press-fitted into the chamber 114 to thereby secure the bobbin140 to the housing 108. The first end plate 142 includes a threadedportion 148. The threaded portion 148 is similar to the threaded portion112 and may be configured to be mated with a threaded aperture definedin the stem 104. Similar to the bobbin 118 described above in regard toFIGS. 5 a and 5 b, the bobbin 140 is positioned and secured in thechamber 114 of the housing 108 such that the reference plane 120 formedfrom the coil turns of the secondary coil 116 are substantially parallelwith the sagittal plane 80 of the patient 54 when the tibial tray 100 isproperly implanted in the patient 54. Again, in such a configuration,when the patient 54 passes through the passageway 78 of the gate 70 asillustrated in FIG. 3, the reference plane 120 defined by the coil turnsof the secondary coil 116 of the orthopaedic implant 52 (e.g., thetibial tray 100) is substantially parallel with the reference planes 82,84 defined by the coil turns of the primary/receiver coils 50.

Although the secondary coil 116 has been described above in regard toseveral illustrative embodiments, it should be appreciated that in otherembodiments the secondary coil 116 may be embodied as any type of coilcapable of receiving power from a primary coil (e.g., the primary coils50). For example, the secondary coil 116 may be embodied as a radiofrequency identification (RFID) coil. In such embodiments the RFID coilmay be positioned in the chamber 114 of the housing 108 or,alternatively, secured to the orthopaedic implant 52 (e.g., the tibialtray 100) in any location such that a reference plane defined by thecoil turns of the RFID coil is substantially parallel with the sagittalplane 80 of the patient 54 when the orthopaedic implant 52 is properlyimplanted in the patient 54.

Referring now to FIG. 6, in one embodiment, the secondary coil 116 formsa portion of an electronic circuit 150, which is included in theorthopaedic implant 52 (e.g., the tibial tray 100). The electroniccircuit 150 is secured to the orthopaedic implant 52 in a location suchthat the electronic circuit 150 is not adversely affected by bodilytissue or fluid and does not adversely affect the structural integrityof the orthopaedic implant 52. For example, in embodiments wherein theorthopaedic implant 52 is embodied as the tibial tray 100, theelectronic circuit 150 may be positioned in the chamber 114 of thehousing 108 and secured to the housing 108 in a manner similar to thebobbin 118. Additionally or alternatively, a portion of the electroniccircuit 150 may be positioned in the stem 104 and/or platform 102 of thetibial tray 100.

The circuit 150 also includes a processing circuit 152, switchingcircuitry 154, and transmitter circuitry 156. The processing circuit 152may be embodied as any type of processing circuit and may include anynumber of electronic devices. Illustratively, the processing circuit 152includes a processor 158 and a memory device 160. The processor 158 maybe embodied as any type of processor including, for example, discreteprocessing circuitry (e.g., a collection of logic devices), generalpurpose integrated circuit(s), and/or application specific integratedcircuit(s) (i.e., ASICS). The memory device 160 may be embodied as anytype of memory device and may include one or more memory types, such as,random access memory (i.e., RAM) and/or read-only memory (i.e., ROM).Illustratively, the implant identification data is stored in the memorydevice 160. The switching circuitry 154 may be embodied as anycollection of electrical and/or mechanical device capable of selectivelyconnecting the secondary coil 116 to the transmitter circuitry 156 orthe processing circuit 152. The transmitter circuitry 156 may beembodied as any type of transmitter circuitry capable of transmittingthe implant identification data from the orthopaedic implant 52 to theprimary/receiver coil 50 or other receiver. For example, the transmittercircuitry 156 may be embodied as an inductor-capacitor (LC) circuit, aresonating crystal circuit, or the like. The transmitter circuitry 156may use any carrier frequency capable of transmitting the identificationdata. In one particular embodiment, the transmitter circuitry 156 isconfigured to transmit the implant identification data using a lowcarrier frequency such as, for example, a frequency of about 125kilohertz to about 143 kilohertz or from about 13.553 megahertz to about13.567 megahertz. However, it should be appreciated that in otherembodiments, other frequencies may be used by the transmitter circuitry156 to transmit the implant identification data.

The processing circuit 152 is communicatively coupled to the switchingcircuitry 154 via a number of communication links 162 and to thetransmitter circuitry 156 via a number of communication links 164. Theswitching circuitry 154 is communicatively coupled to the transmittercircuitry 156 via a number of communication links 166 and to thesecondary coil 116 via a number of communication links 168. Thecommunication links 162, 164, 166, 168 may be any type of communicationlinks capable of providing communication between the processing circuit152, the switching circuitry 154, the transmitter circuitry 156 and thesecondary coil 116. For example, the communication links may be embodiedas any number of wires, cables, fiber optic cables, printed circuitboard traces, vias, or the like.

In use, when the secondary coil 116 is inductively coupled to theprimary coil 50, an amount of energy is transferred to the secondarycoil 116. The switching circuitry 154 connects the secondary coil 116 tothe processing circuit 152 (i.e., the communication links 168 and 162are electrically connected to each other) to thereby power theprocessing circuit 152. In response to the power signal received fromthe secondary coil 116, the processing circuit 152 controls theswitching circuitry 152 to connect the transmitter circuitry 156 to thesecondary coil 116 (i.e., the communication links 166 and 168 areelectrically connected to each other). The processing circuit 152subsequently controls the transmitter circuitry 156 to transmit theimplant identification data using the secondary coil 116 as atransmitter coil.

Referring now to FIG. 7, in another embodiment, the electronic circuit150 may include one or more implant sensors 170 and a separate antenna172. The implant sensors 170 may be any type of sensors such as, forexample, pressure sensors, load sensors, temperature sensors, strainsensors, hall-effect sensors, or the like. The implant sensors 170 maybe secured to the orthopaedic implant 52 or may be positioned remotelytherefrom. The antenna 172 may be embodied as any type of antenna usableby the transmitter circuitry 156 to transmit the implant identificationdata and implant sensor data produced by the implant sensors 170. In oneembodiment, the antenna 172 is embodied as a monopole antenna positionedso as to extend beyond the metal portion of the orthopaedic implant 52.For example, the antenna 172 may be embedded in a plastic portion of theorthopaedic implant 52 such as a bearing surface or the like.Alternatively, a metal portion of the orthopaedic implant 52 may be usedas the antenna 172 as described in U.S. patent application Ser. No.10/880,003, entitled “System and Method for Bidirectional Communicationwith an Implantable Medical Device using an Implant Component as anAntenna”, which was filed on Jun. 29, 2004 by Jason T. Sherman et al.,the entirety of which is incorporated herein by reference.

The processing circuit 152 is communicatively coupled to the implantsensors 170 via a number of communication links 174. The processingcircuit 152 is also coupled to the transmitter circuitry 156 via anumber of communication links 176 and to the secondary coil 116 via anumber of communication links 178. The transmitter circuitry 156 is alsocoupled to the antenna 172 via a number of communication links 180. Thecommunication links 174, 176, 178, 180 may be any type of communicationlinks capable of providing communication between the processing circuit152, the implant sensors 170, the transmitter circuitry 156, the antenna172, and the secondary coil 116.

In such embodiments, the processing circuit 152 is configured to receivepower from the secondary coil 116 when the secondary coil 116 isinductively coupled to the primary coil 50 (e.g., when the patient 54 iswalking through the passageway 78 of the gate 70) or to an alternativeprimary coil (e.g., a portable primary coil usable by a surgeon toretrieve implant sensor data at any location such as in an examinationroom). In response to a power signal received from the secondary coil116, the processing circuit 152 is configured to receive an outputsignal(s) from the implant sensors 170 and transmit the output signal(s)and the implant identification data, which may be retrieved from thememory device 160, using the transmitter circuitry 156 and the antenna172. In some embodiments, such as those embodiments wherein the implantsensors 170 are magnetic-type sensors such as Hall-effect sensors, theprocessing circuit 152 may be configured to wait until the primary coil50 has been deactivated or the orthopaedic implant 52 is otherwise notaffected by an electromagnetic field prior to accepting or takingmeasurements from the implant sensors 170.

In embodiments wherein the electronic circuit 150 includes one or moreimplant sensors 170, the transmitter circuitry 156 may be configured totransmit the implant identification data and the implant sensor datausing a higher frequency than those embodiments wherein an implantsensor 170 is not included due to the increase in the overall amount ofdata transferred in the allotted time. For example, the transmittercircuitry 156 may be configured to transmit the implant identificationdata and the implant sensor data using a carrier frequency of about 2.4gigahertz to about 2.483 gigahertz. However, it should be appreciatedthat in other embodiment, other high frequencies may be used by thetransmitter circuitry 156 to transmit the implant identification dataand the implant sensor data.

Referring now to FIG. 8, in another embodiment, the network 34 of thesystem 10 may be embodied as a wireless network such as a wireless localarea network (WLAN). In such embodiments, the system 10 may include awireless receiver 190. The wireless receiver 190 may be embodied as anytype of wireless receiver capable of receiving the identification dataand implant sensor data from the orthopaedic implant 52. For example,the wireless receiver may be embodied as a wireless router. In suchembodiments, the transmitter circuitry 156 of the orthopaedic implant 52is configured to transmit the implant identification data and theimplant sensor data, if available, using the frequency of the wirelessnetwork. For example, in one particular embodiment, the transmittercircuitry 156 is configured to transmit the implant identification dataand the implant sensor data using a carrier frequency in the 2.4gigahertz unlicensed band (e.g., using a carrier frequency in the rangeof about 2.4 gigahertz to about 2.483 gigahertz). Additionally oralternatively, in some embodiments, the transmitter circuitry 156 may beconfigured to transmit the implant identification data and the implantsensor data using a Bluetooth transmission protocol. Regardless, thewireless receiver 190 is configured to receive the implantedidentification data and the implant sensor data, if available,transmitted by the orthopaedic implant 52.

The wireless receiver 190 may be communicatively coupled to thecontroller 12 via a number of communication links 192 such as wires,cables, or the like. Alternatively, in embodiments wherein the wirelessreceiver 190 is a wireless router, the receiver 190 may becommunicatively coupled to the controller 12 via a wirelesscommunication link 194 and the wireless network 34.

In operation, the electronic circuits 150 of the orthopaedic implants 52may execute an algorithm 250 for transmitting implant data asillustrated in FIG. 9. The algorithm 250 begins with a process step 252in which the processing circuit 152 of the circuit 150 activates when apower signal has been received from the secondary coil 116 via thecommunication links 168, 162 or 178. In embodiments wherein the circuit50 includes a number of implant sensors 170, the algorithm 250 advancesto process step 254 when a power signal has been received. In processstep 254 the processing circuit 152 receives output data from theimplant sensors 170 via the communication link 174. Depending on thetype of the implant sensors 170, the output data may be, for example,pressure data, temperature data, or the like.

Subsequently, in process step 256, the processing circuit 152 transmitsthe implant identification data. To do so, the implant identificationdata may be retrieved from the memory device 160. As discussed above inregard to FIG. 1, the implant identification data may be embodied as acode or password, which is digitally stored in the memory device 160. Inembodiments wherein the secondary coil 116 is also used as an antennacoil (FIG. 6), the processing circuit 152 also controls the switchingcircuitry 154 to connect the transmitter circuitry 156 to the secondarycoil 116 in process 256. The implant identification data is subsequentlytransmitted by the circuitry 150 using the transmitter circuitry 156 andthe secondary coil 116 as an antenna coil. Alternatively, in embodimentswherein the circuitry 150 includes a separate antenna 172 (FIG. 7), theprocessing circuitry 152 controls the transmitter circuitry 156 totransmit the implant identification data using the antenna 172.

Once the implant identification data has been transmitted in processstep 256, the output signals received from the implant sensors 170 istransmitted in process step 258. To do so, the processing circuitry 152controls the transmitter circuitry 156 to transmit the implantidentification data using the antenna 172. Once the implantidentification data and the output signals from the implant sensors 170,if any, have been transmitted, the algorithm 250 loops back to processstep 252 in which the processing circuit 252 determines if another powersignal has been received or is still being received from the secondarycoil 116. In this way, the electronic circuit 150 is configured toperiodically transmit the implant identification data (and implantsensor data) while secondary coil is indicatively coupled to the primarycoil. That is, while the patient 54 is walking though or standing in thepassageway 78 of the gate 70, the electronic circuit 150 of theorthopaedic implant 52 will transmit the implant identification data andthe output signals from the implant sensors 170 if available.

In use, the system 10 may execute an algorithm 300 for managingpatient-related data as illustrated in FIG. 10. The algorithm 300 beginswith a process step 302 in which the primary coil 50 of the implantidentification reader 14 (e.g., the gate 70) is inductively coupled withthe secondary coil 116 of the orthopaedic implant 52. To do so, thecontroller 12 is configured to transmit a power signal to the primarycoil 50 via the communication link 16 to thereby energize the coil 50.In response the primary coil 50 generates an electromagnetic field,which is received by the secondary coil 116 of the orthopaedic implant52. It should be appreciated that the controller 12 may be configured tocontinuously energize the primary coil 50, periodically energize theprimary coil 50, or selectively energize the primary coil 50. Forexample, in some embodiments, the implant identification reader 14 mayinclude a pressure or motion sensor configured to determine the presenceof the patient 54. In such embodiments, the pressure, motion, or othersensor output is transmitted to the controller 12 and, in response, thecontroller 12 transmits the power signal to the primary coil 50. In thisway, the primary coil 50 is only energized when a patient 54 is presentsuch as when a patient 54 is walking through or standing in thepassageway 78 of the gate 70.

Once the power signal has been transmitted to the power coil 50, thecontroller 12 determines if any implant identification data is available(i.e., if any implant identification data is being transmitted) inprocess step 304. If not, the algorithm 300 loops back to the processstep 302 wherein the controller 12 continuously, periodically, orselectively transmits the power signal to the primary coil 50. However,if implant identification data is being transmitted by the orthopaedicimplant 54, the algorithm 300 advances to process step 306. In processstep 306, the implant identification data is received from theorthopaedic implant. To do so, in embodiments wherein the primary coil50 is also a receiving coil (FIG. 1), the implant identification data isreceived by the primary/receiving coil 50 and transmitted to thecontroller 12 via the communication link 16. However, in embodimentswherein the system 10 includes the wireless receiver 190 (FIG. 8), theimplant identification data is received by the wireless receiver 190 andtransmitted to the controller 12 via the communication link 192 or viathe communication link 194, the wireless network 34, and thecommunication link 36.

Similarly, in embodiments wherein the orthopaedic implant 52 includesthe number of implant sensors 170, the controller 12 receiving implantsensor data transmitted by the orthopaedic implant 52 in process step308. The controller 12 may receive the implant sensor data in a mannersimilar to the implant identification data. That is, in embodimentswherein the primary coil 50 is also a receiving coil (FIG. 1), theimplant sensor data is received by the primary/receiving coil 50 andtransmitted to the controller 12 via the communication link 16.Alternatively, in embodiments wherein the system 10 includes thewireless receiver 190 (FIG. 8), the implant sensor data is received bythe wireless receiver 190 and transmitted to the controller 12 via thecommunication link 192 or via the communication link 194, the wirelessnetwork 34, and the communication link 36.

Once the implant identification data (and implant sensor data) has beenreceived by the controller 12, the algorithm 300 advances to processstep 310. In process step 310, the controller 12 receives security codedata. The security code data may be entered automatically or manuallyand may be embodied as any type of security code data such as apassword, digital code, or other data. For example, in some embodimentsthe security code data is embodied as a digital code stored in a keyfobor the like that may be passed in front of a code reader (not shown) tothereby transmit the security code data. Alternatively, the securitycode data may be embodied as a digital fingerprint or the like, which isentered via a digital fingerprint analyzer. The security code data maybe entered directly into the controller 12 or, in some embodiments, isentered via one of the receptionists client machines 22. In suchembodiments, the controller 12 communicates with the client machine 22to request that the security code data be entered. For example, a promptmay be displayed on a display of the client machine 22. In response, areceptionist, nurse, or other caregiver may be enter a password, swipe akeyfob having the digital security data stored therein, or press afinger on a digital fingerprint analyzer coupled to the client machine22. Regardless of the type of security code data entered, the clientmachine 22 transmits the security code data to the controller 12 via thecombination link 38, the network 34 and the communication link 36.Alternatively or additionally, in some embodiments, the patient 54 isrequested to enter security code data such as a password, personalidentification number, or the like. The patient 54 may enter thesecurity code data via a client machine or the like located in thewaiting area of the doctor's office or hospital wherein the system 10 isincorporated.

Once the controller 12 has received the security code data, thecontroller 12 determines if the security code data is valid in processstep 312. To do so, the controller 12 may retrieve a security code listor the like from the database 32 and compare the received security codedata to one or more of the security codes retrieved from the database32. If the security code data is not valid, the algorithm 300 loops backto the process step 310 wherein the controller 12 waits for additionalsecurity code data to be entered. If, however, the security code data isvalid, the controller 12 advances to process step 314 whereinpatient-related data is retrieved from the database 32. To do so, thecontroller 12 accesses the database 32 via the communication links 36,the network 34, and the communication link 48 and retrieves thepatient-related data that is associated with the implant identificationdata received in process step 306. That is, the patient-related data isstored in the database 32 in association with or indexed by the implantidentification data. The controller 12 accesses the appropriatepatient-related data based on implant identification data. In this way,the patient-related data is only retrieved if the security code data hasbeen entered and is valid.

Once the patient-related data has been retrieved in process step 314,the controller 12 determines if any of the patient-related data requiresupdating. For example, the controller 12 may determine if any of thepatient-related data is missing such as the patient's 54 address or thelike. Additionally or alternatively, the controller 12 may determinethat the patient-related data requires updating if a portion, such asthe patient's 54 address, has not been updated for a predeterminedperiod of time. If the patient-related data does require updating, thecontroller 12 is configured to retrieve an electronic patientinformation form from the database 32 in process step 318. The patientinformation form includes a number of data fields wherein the patient 54may supply patient-related information such as address information,insurance information, or the like. In addition, the controller 12 maybe configured to populate a portion of the electronic form with thepatient-related data. For example, the controller 12 may populate thename and address data fields of the electronic form with the name andaddress information included in the patient-related data that wasretrieved in process step 314.

Once the electronic patient information form has been retrieved andpopulated in process step 318, the algorithm 300 advances to processstep 320. In process step 320, the controller 12 transmits the populatedelectronic form to the printer 28 via the communication link 36, thenetwork 34, and the communication link 44. In response, the printer 28prints a “hard copy” of the electronic patient information form so thatthe patient 54 may supply any required patient information. Once thepatient 54 has filled out the printed patient information form, thepatient information supplied by the patient 54 on the form may beentered into the system 10. To do so, in one embodiment, a receptionist,nurse, or other caregiver may manually enter the data from the patientinformation form into one of the receptionist's client machines 22. Inresponse, the client machine 22 transmits the information to thecontroller 12 via the communication link 38, the network 34, and thecommunication link 36. In response to the new patient information, thecontroller 12 is configured to update the patient-related data with thenew patient information by accessing the database 32 and storing theupdated or new patient information in the database 32.

In other embodiments, the patient-related data may be updatedelectronically without the use of a printed form. In such embodiments,the controller 12 is configured to transmit the retrieved (andpopulated) electronic form to, for example, an electronic tablet orother data entry device usable by the patient 54. The controller 12 maytransmit the electronic form using a wireless or wired signal dependingon the type of data entry device used. The patient 54 may thenpersonally update the patient-related data and/or provide additionalpatient data. Once complete, the controller 12 may be configured toreceive the updated patient information from the electronic tablet ordata entry device and update the patient-related data with the newpatient information. In this way, the updating of the patient-relatedinformation is automated and a nurse or receptionist is not required tomanually enter the new patient information from a printed form.

Referring back to process step 316, if the patient-related data does notrequired updating, the algorithm 300 advances to process step 324. Inprocess step 324, the controller 12 is configured to update a patientqueue with the name of the patient 54 as determined by thepatient-related data in process step 314. That is, the controller 12 isconfigured to extract the name of the patient 54 from thepatient-related data and add the patient's name to the bottom of thepatient queue (if the patient queue is a first in-first out type ofqueue). The patient queue may be stored on, for example, one or more ofthe receptionists client machines 22 such that the receptionist maymonitor and adjust the patient queue. Once the patient queue has beenupdated with the patient 54, the controller 12 determines if a patientroom is available in process step 326. To do so, the controller 12 maymonitor the patient queue and subtract patient's names from the queue aspatient rooms are assigned to the patients. The controller 12 may alsobe configured to adjust the patient queue based on specific patientrooms, medical equipment located therein, and/or other parameters. Forexample, if a specific patient room is used for particular types ofexaminations or surgical procedures, the controller 12 may be configuredto adjust the queue such that the particular patient room is assigned tothe patient scheduled for such examination or procedure. Additionally,if the examination or medical procedure requires particular medicalequipment, the controller 12 may be configured to adjust the patientqueue such that the patient room wherein the particular medicalequipment is located is assigned to the patient scheduled for suchexamination or procedure.

Once the patient's 54 name is at the top of the patient queue and a roomis available, the algorithm 300 advances to process step 328. In processstep 328, the controller 12 is configured to notify the receptionistthat a patient room is available for the patient 54. To do so, thecontroller 12 may transmit an electronic signal or notification to oneor more of the receptionist's client machines 22. Once so notified, thereceptionist may notify the patient 54 and escort the patient 54 to theassigned patient room. Additionally, in some embodiments, the controller12 is configured to activate the public address system 30 to notify thepatient that a patient room is available in process step 330. To do so,the controller 12 transmits data to the public address system 30 via thecommunication link 36, the network 34, and the communication link 46.For example, in embodiments wherein the public address system 30 isembodied as display device, the controller 12 is configured to transmitthe patient's 54 name and patient room number to the public addresssystem 30 to cause the patient's 54 name and patient room number to bedisplayed to the patient 54.

Once the receptionist and patient has been notified that a patient roomis available, the algorithm 300 advances to process step 332. In processstep 332, the controller 12 is configured to transmit thepatient-related data to the remote client machine 24 associated with thepatient room assigned to the patient 54. For example, in embodimentswherein the remote client machines 24 is located in the patient rooms,the controller 12 is configured to transmit the patient-related data tothe remote client machine located in the patient room that has beenassigned to the patient 54. The controller 12 may transmit thepatient-related data to the remote client machine 24 via thecommunication links 36, the network 34, and the communication links 40.In addition, the controller 12 transmits patient-related data to theportable media device 26 used by the doctor or caregiver that is toexamine or operate on the patient 54. The controller 12 may transmit thepatient-related data to the portable media device 26 via thecommunication links 36, the network 34, and the communication links 42.In this way, the doctor or caregiver may review, update, and supply newpatient-related data via the remote client machine 24 located in thepatient room or the portable media player prior to, during, or after thepatient examination and/or surgery. In embodiments wherein theorthopaedic implant 52 is configured to transmit implant sensor data,the controller 12 is also configured to transmit the implant sensor datato the remote client machine 24 and the portable media device 26 inprocess step 334.

Once the patient-related data and implant sensor data, if available, hasbeen transmitted to the remote client machine 24 and the portable mediadevice 26, the algorithm 300 determines if the patient appointment iscompleted in process step 336. To do so, the controller 12 may monitorthe remote client machine 24 located in the assigned patient room and/orthe portable media device 26 for notification from the doctor orcaregiver that the appointment is complete. If so, the algorithm 300advances to process step 338 wherein the controller 12 receives any newor updated patient-related information entered by the doctor orcaregiver prior to, during, or subsequent to the examination or surgery.For example, during the examination, the doctor may enter notes into theclient machine 24 located in the patient room and/or the doctor'sportable media device 26. It should be appreciated that any type of datamay be supplied to the client machine 24 and/or portable media device 26prior to, during, or subsequent to the patient examination or surgery.For example, caregiver notes, prescriptions, patient symptoms, X-rays,or the like may be recorded. Regardless, once the appointment iscomplete any data entered by the doctor or other caregiver istransmitted to the controller 12 in process step 338.

Subsequently, in process step 340, the controller 12 is configured toupdate the patient database 32 with the new patient-related datareceived in process step 338. To do so, the controller 12 transmits thenew patient-related data to the database 30 via the communication links36, the network 34, and the communication links 48. The newpatient-related data is stored in the database 30 in association withthe implant identification data received in process step 306.

Once any new patient-related data is stored in process step 340, thecontroller 12 schedules the patient 54 for a next appointment in processstep 342. To do so, the controller 12 may be configured to transmit anotification to one of the receptionist's client machines 22 that afollow-up appointment is required. The receptionist may then communicatewith the patient 54 to schedule the next appointment. Alternatively, ifthe doctor or caregiver has already supplied a date for the nextappointment, the controller 12 may automatically schedule patient 54 forthe appointment. For example, the controller 12 may be configured toenter the patient's 54 name, as determined from the patient-related dataretrieved in process step 306, into an electronic calendar, which may beviewable on one or more of the receptionist's client machines 22. Inaddition, a confirmation of the scheduled appointment may be printed onthe printer 28 for the patient's 54 records.

Although the process steps of the algorithm 300 are illustrated in FIGS.10 a-10 c according to a particular sequential order, it should beappreciated that many of the process steps may be performed in any orderand/or performed contemporaneously with each other. For example, thepatient queue may be updated with the new patient prior to determiningif the retrieved patient-related data requires updating rather thansubsequent thereto. Additionally, although the orthopaedic implant 52has been described as a tibial tray in one illustrative embodiment, itshould be appreciated that in other embodiments the orthopaedic implant52 may be embodied as any type of orthopaedic implant. For example, theorthopaedic implant 52 may be embodied as femoral orthopaedic implant, ahip joint orthopaedic implant, a shoulder joint orthopaedic implant, orthe like.

While the disclosure has been illustrated and described in detail in thedrawings and foregoing description, such an illustration and descriptionis to be considered as exemplary and not restrictive in character, itbeing understood that only illustrative embodiments have been shown anddescribed and that all changes and modifications that come within thespirit of the disclosure are desired to be protected.

There are a plurality of advantages of the present disclosure arisingfrom the various features of the systems and methods described herein.It will be noted that alternative embodiments of the systems and methodsof the present disclosure may not include all of the features describedyet still benefit from at least some of the advantages of such features.Those of ordinary skill in the art may readily devise their ownimplementations of the systems and methods that incorporate one or moreof the features of the present invention and fall within the spirit andscope of the present disclosure as defined by the appended claims.

1. An orthopaedic implant comprising: a housing having a chamber definedtherein; and a secondary coil having a number of turns positioned so asto define a reference plane, the secondary coil being positioned in thecamber of the housing such that the reference plane is substantiallyparallel with a sagittal plane of a body of a patient when theorthopaedic implant is implanted in the patient.
 2. The orthopaedicimplant of claim 1, wherein the orthopaedic implant is a tibial tray andthe housing is a stem of the tibial tray.
 3. The orthopaedic implant ofclaim 1, further comprising a processing circuit electrically coupled tothe secondary coil and configured to receive a power signal from thesecondary coil when the secondary coil is inductively coupled with aprimary coil.
 4. The orthopaedic implant of claim 3, further comprising:a wireless transmitter coupled to the processing circuit; and an antennacoil electrically coupled to the wireless transmitter, wherein theprocessing circuit is configured to control the wireless transmitter totransmit implant identification data in response to the power signalusing the antenna coil.
 5. The orthopaedic implant of claim 4, whereinthe transmitter is configured to transmit the implant identificationdata at a frequency of about 2.4 gigahertz.
 6. The orthopaedic implantof claim 4, wherein the transmitter is configured to transmit theimplant identification data using a wireless local area networkfrequency.
 7. The orthopaedic implant of claim 4, wherein the processingcircuit and the transmitter are configured to transmit the implantidentification data using a Bluetooth transmission protocol.
 8. Theorthopaedic implant of claim 4, further comprising a sensor electricallycoupled to the processing circuit, wherein the processing circuit isconfigured to: receive an output signal from the sensor; and control thewireless transmitter to transmit the output signal in response to thepower signal using the antenna coil.
 9. The orthopaedic implant of claim8, wherein the sensor is a sensor selected from the group consisting ofa pressure sensor, a load sensor, a temperature sensor, and ahall-effect sensor.
 10. The orthopaedic implant of claim 8, wherein thetransmitter is configured to transmit the output signal at a frequencyof about 2.4 gigahertz.
 11. The orthopaedic implant of claim 8, whereinthe transmitter is configured to transmit the output signal using awireless local area network frequency.
 12. The orthopaedic implant ofclaim 8, wherein the processing circuit and the transmitter areconfigured to transmit the output signal using a Bluetooth transmissionprotocol.
 13. A method for transmitting data from an orthopaedicimplant, the method comprising: receiving a power signal generated by aprimary coil with a secondary coil of the orthopaedic implant; receivingan output signal from a sensor of the orthopaedic implant in response tothe power signal; and wirelessly transmitting implant identificationdata and the output signal in response to the power signal.
 14. Themethod of claim 13, wherein receiving a power signal comprisestranscutaneously receiving an amount of energy from the primary coilwith the secondary coil.
 15. The method of claim 13, wherein receivingan output signal from a sensor comprises receiving an output signal froma sensor selected from the group consisting of a pressure sensor, a loadsensor, a temperature sensor, and a hall-effect sensor.
 16. The methodof claim 13, wherein wirelessly transmitting the implant identificationdata and the output signal comprises wirelessly transmitting the implantidentification data and the output signal at a frequency of about 2.4gigahertz.
 17. The method of claim 13, wherein wirelessly transmittingthe implant identification data and the output signal compriseswirelessly transmitting the implant identification data and the outputsignal using a wireless local area network frequency.
 18. The method ofclaim 13, wherein wirelessly transmitting the implant identificationdata and the output signal comprises wirelessly transmitting the implantidentification data and the output signal using a Bluetooth transmissionprotocol.
 19. The method of claim 13, wherein wirelessly transmittingthe implant identification data and the output signal compriseswirelessly transmitting the implant identification data and the outputsignal to a wireless router.
 20. The method of claim 13, furthercomprising powering a processing circuit of the orthopaedic implant withthe power signal.
 21. A system for managing patient-related data, thesystem comprising: an orthopaedic implant configured to transmit implantidentification data and implant sensor data in response to a powersignal; a primary coil configured to inductively couple with a secondarycoil of the orthopaedic implant to provide the power signal to theorthopaedic implant; a wireless receiver configured to receive theimplant identification data and the implant sensor data transmitted bythe orthopaedic implant; a processor coupled to the wireless receiver;and a memory device electrically coupled to the processor, the memorydevice having stored therein a plurality of instructions, which whenexecuted by the processor, cause the processor to: receive the implantidentification data and the implant sensor data from the wirelessreceiver; and retrieve patient-related data from a database based on theimplant identification data.
 22. The system of claim 21, wherein theprimary coil is coupled to a gate configured to allow patients to traveltherethrough.
 23. The system of claim 21, wherein the wireless receiveris a wireless router.
 24. The system of claim 21, further comprising awireless network, wherein the orthopaedic implant is configured totransmit the implant identification data and the implant sensor data tothe wireless receiver over the wireless network.
 25. The system of claim21, wherein the orthopaedic implant is configured to transmit theimplant identification data and the implant sensor data at a frequencyof about 2.4 gigahertz.
 26. The system of claim 21, wherein theorthopaedic implant is configured to transmit the implant identificationdata and the implant sensor data using a Bluetooth transmissionprotocol.
 27. The system of claim 21, wherein to retrievepatient-related data comprises to retrieve the patient-related data froma database of a hospital network.
 28. The system of claim 21, whereinthe plurality of instructions further cause the processor to update anelectronically-stored patient queue based on the retrieving step. 29.The system of claim 28, wherein the plurality of instructions furthercause the processor to assign a patient room to a patient identified bythe patient-related data based on the electronically-stored patientqueue.
 30. The system of claim 29, wherein the plurality of instructionsfurther cause the processor to transmit the patient-related data and theoutput sensor data to a client machine located in the patient room. 31.The system of claim 30, wherein the plurality of instructions furthercause the processor to: determine the availability of the patient roombased on the electronically-stored patient queue; and provide anelectronic notification if the patient room is available.
 32. The systemof claim 31, wherein to provide an electronic notification comprises toactivate a public address system.
 33. The system of claim 31, wherein toprovide an electronic notification comprises to display a name of apatient identified by the patient-related data on a display screen. 34.The system of claim 21, wherein the plurality of instructions furthercause the processor to transmit the patient-related data and the implantsensor data to a client machine over a wireless network.
 35. The systemof claim 21, wherein the plurality of instructions further cause theprocessor to transmit the patient-related data to a portable mediadevice.
 36. The system of claim 21, wherein the plurality ofinstructions further cause the processor to: receive security code data;and determine the validity of the security code data.
 37. The system ofclaim 36, wherein to determine the validity of the security code datacomprises to compare the security code data to electronically storedsecurity code data.
 38. A system comprising: a gate having a passagewayand a primary coil formed from a number of first coil turns positionedso as to define a first reference plane; and an orthopaedic implanthaving a secondary coil formed from a number of second coil turnspositioned so as to define a second reference plane, the secondary coilbeing positioned in the orthopaedic implant such that the secondreference plane is substantially parallel with the first reference planewhen the orthopaedic implant is implanted in a body of a patient and thepatient is traveling through the passageway.
 39. The system of claim 38,wherein the first reference plane and the second reference plane aresubstantially parallel with a sagittal plane of the body of the patientwhen the orthopaedic implant is implanted in a body of a patient and thepatient is traveling through the passageway.